home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-06-08 | 53.4 KB | 1,272 lines |
- <paper long=11in short=8.5in><pt12><leading line=14pt para=7pt><qz>
- <margin top=1in left=1in right=7.75in bottom=10.25in><xr><ip><qz>
- <column count=1 gutter=0><margin header=.55in><qz>
- <footer>
-
- <end>
- <pt8>RPT 2.2C 31/3/91<qr3in>
- <ib.75in><qz>
- <line thick=4pt><ql28pt>
- <ab><pt24>RUBICON PUBLISHER<qc18pt>
- <pt14>VERSION 2.2C<qc36pt>
- <pt30>TUTORIAL<pt12><xb><qc14pt>
- <line thick=4pt><ql3in>
- <leader char=32 width=0.75><ib><qz>
- <line thick=2pt><ql15pt>
- Rubicon Computer Labs Inc.<jf>2 rue des Pommiers<jf>Hull, P.Q., Canada J8Z 2M2<qj13pt>
- <pt10>Telephone & Fax:<N>(819)770-4317<jf>CompuServe:<N>71307,1212<qj10pt>
- <line thick=2pt><ql1pt>
- <pn=0><pt12><qz>
- <header>
- <margin left=1in right=7.75in><pt12><qz>
- <ai>The Rubicon Publisher Tutorial<qz>
- Page <pn><xi><qr>
- <end>
- <np>
- <ql1in>
- <ab><pt24>T<pt18>ABLE OF <PT24>C<PT18>ONTENTS<pt14><xb><qc36pt>
- <il0.75in><ir.5in><qz>
- <line thick=2pt><ql24pt>
- T.1<N>Introduction<ql24pt>
- T.2<N>Installation and Hardware Setup<ql24pt>
- T.3<N>Preliminaries<ql24pt>
- T.4<n>Text Files<ql24pt>
- T.5<N>Style Sheets and the <60>Include <.><.><.><62> Tag<ql24pt>
- T.6<N>Lesson 1<ql24pt>
- T.7<N>Lesson 2<ql24pt>
- T.8<N>Lesson 3<ql24pt>
- T.9<N>Lesson 4<ql24pt>
- T.10<N>Lesson 5<ql24pt>
- T.11<N>Lesson 6<ql24pt>
- T.12<N>Publishing Your Own Documents<ql24pt>
- T.13<N>Solving Problems<ql24pt>
- T.14<N>Conclusion<ql24pt>
- <line thick=2pt><ql24pt>
- <il><ir><pt12><ql1.5in>
- (c) <itl>Copyright Rubicon Computer Labs Inc., 1991<ql16pt>
- <ai>All rights reserved.<xi><ql>
- <il><qz>
- <np>
- <ab><pt18>T.1<N>Introduction<pt12><xb><ql>
-
- To understand what the Rubicon Publisher is, and how it works, imagine
- that you are living about 50 years ago, before computers were invented.
- You are faced with the job of publishing a document by the traditional
- method: namely, preparing the text in the form of a ``manuscript'', and
- sending the manuscript to a traditional printing shop, where the
- printers will set it in type and print it. Naturally, you have to
- provide the printers with written instructions specifying the size of
- paper to be used, the locations of the margins, the number of columns to
- appear on each page, the width of the ``gutter'' (space) between
- columns, the type ``fonts'' (typefaces, sizes and weights of type) to be
- used, the desired line spacing, and so on. If you are going to use
- enhancements like bold-face printing, underlining or italics, you have
- to indicate the exact points in the text where enhanced printing is to
- start and stop.
-
- You therefore include the necessary printing instructions in the
- ``manuscript'' of your document. The instructions concerning page format
- and layout naturally must appear at the beginning of the manuscript.
- Instructions concerning font changes, enhancements, etc. are of course
- placed at the points where the changes are desired. To avoid
- misunderstandings, you give your instructions using technical
- typesetting terms. To avoid any confusion between the printing
- instructions and the text which is to be printed, you enclose all
- instructions in triangular brackets: ``<60>instruction<62>''.
-
- When you have completed the manuscript with all necessary instructions
- included, you send it to the printers. They set the document in type,
- following the instructions you have given them, and then print a
- specimen copy (known as a ``proof'') which they send to you for your
- approval. If corrections are needed, you enter the necessary
- instructions, and send the document back to the printers, who make the
- required changes, and print a second ``proof'' copy for your inspection.
- If necessary, this process is repeated until the printers produce a
- ``proof'' which is satisfactory.
-
- Publishing a document using the Rubicon Publisher follows this
- traditional publishing method, but the old-fashioned printing shop and
- its human employees have been replaced by the Rubicon Publisher program,
- installed on your own personal computer, and your dot-matrix, ink-jet or
- laser printer. You prepare your document as a ``manuscript'' in the form
- we have described, with all necessary printng instructions, using your
- personal computer and whatever word-processing program you find most
- convenient. However, when you have finished it, instead of sending it
- to a printing shop, you simply submit the computer file containing it to
- the Rubicon Publisher, which sets it in type electronically, following
- the instructions you have provided, and, in a matter of minutes,
- generates a ``preview'' of your document on your computer screen, or
- prints out a copy on your computer printer for immediate inspection.
-
- Of course, the Rubicon Publisher cannot know whether your instructions
- are <ai>reasonable<xi> or not. The Publisher will simply do what you
- have told it to do, unless it is actually impossible. You must therefore
- provide it with instructions that are complete, correct, and exact. As
- you will find by following the Tutorial, this is not difficult, but it
- does require reasonable attention to detail.
-
- Learning to use the Rubicon Publisher successfully is <ai>easy<xi>, as
- long as you keep in mind what it is that you are doing: you are
- preparing a manuscript with printing instructions, and sending it to an
- electronic ``printing shop'' which happens to be sitting right there on
- your desk.
-
- The Rubicon Publisher consists of two main parts: (1) a typesetting
- language consisting of ``tags'' (instructions) concerning page layout,
- font selection, etc., which can be inserted by the user at appropriate
- locations in a computer text file; and (2) an executable ``batch
- processor'' program which, upon command, accepts a computer text file
- including such tag instructions, interprets and acts on the tags, and
- either previews the results on your computer screen, or transmits the
- results directly to a printer (or, optionally, to a disk file for later
- transmission to the printer).
-
- This Tutorial is designed to teach you how to use the Publisher. The
- best way to learn how to do anything is by actually doing it, and the
- Tutorial follows this approach by taking you, step by step, through the
- preparation and publication of some specimen documents.
-
- <ql18pt>
- <ab><pt18>T.2<N>Installation and Hardware Setup<pt12><xb><ql>
-
- This Tutorial is designed to be used with Version 2.2C of the Publisher,
- installed in the conventional manner on Drive C by means of the
- installation program, for a printer which will use Rubicon's Trajan and
- Renner fonts, and which is set up to use standard letter-size (8.5x11
- inch) paper. This is the normal setup, and if you did not do anything
- unusual when installing the Publisher, this is what you will have,
- <ai>unless<xi> you selected the LaserJet-3 or PostScript printer option.
-
-
- If your setup differs from this, you will have to amend some of the
- commands and/or Publisher tags specified in the Tutorial, to conform to
- your setup.<ql>
- <pt10><leading line=12pt para=6pt><ih2em><qz>
-
- Note 1:<n>If your Publisher is not installed on Drive C, references to
- Drive C should of course be replaced by references to the drive it is
- installed on.
-
- Note 2:<n>If you are using a LaserJet-3 or Postscript printer, or are
- using third-party soft fonts instead of the Rubicon fonts, the tags
- ``Trajan'' and ``Renner'' should be replaced by tags specifying fonts
- available for your use, typically ``Times'' and ``Helv''.
-
- <pt12><leading line=14pt para=7pt><ih><qz>
- If your computer setup does not support VGA graphics, you will not be
- able to use the Screen Preview feature. However, Screen Preview is
- strictly a convenience feature; if you have it, it may save you some
- time and paper, depending on the kind of work you are doing, but the
- Publisher works perfectly well without it.
-
- <ql18pt>
- <ab><pt18>T.3<N>Preliminaries<pt12><xb><ql>
-
- This Tutorial is self-contained, and it is not necessary to study the
- Concise Manual provided with the Publisher, before proceeding through
- the Tutorial. However, you may get more out of the Tutorial if you take
- a quick look through Section 2 of the Manual, OPERATION AND STRUCTURE
- (file Manual.2), before proceeding.
-
- If you have not already done so, you should PUBLish specimen text files
- SAMPLE_1, SAMPLE_2, <.><.><.> SAMPLE_4, and one or more of the
- ``REGFORM'' files (REGFORM.CAN, REGFORM.US, etc.) which you will find on
- the RUBICON directory. PUBLishing these samples will give you a ``feel''
- for the way the publisher operates. Note: SAMPLE_4 is the table of
- contents for the Concise Manual; the REGFORM files are the licence
- registration forms.
-
- To PUBLish these files:
-
- (a) Make sure your printer is ready and on line.
-
- (b) Log on to the directory RUBICON on Drive C (if you are not already
- there) by entering the command:
-
- CD C:\RUBICON [return]<QC>
-
- (c) enter the command:
-
- PUBL SAMPLE_1 /T [return]<QC>
-
- (d) Wait for Sample_1 to be printed out, and examine the results.
-
- (e) Repeat steps (c) and (d) for SAMPLE_2, SAMPLE_3, SAMPLE_4 and
- the REGFORM file(s).
-
- Remember to <ai>be patient<xi>: the Publisher generally requires <ai>at
- least one and one-half minutes<xi> of processing time, before it starts
- to print, and may require <ai>several minutes,<xi> depending on the
- complexity of the document being published, and the hardware setup being
- used. During much of this processing time, the Publisher may not appear
- to be doing anything.
-
- In this Tutorial, we have included the run-time switch ``/T'' in the
- command line to invoke the ``Tracers'' option (described in Section 2.4 of
- the Manual) so that you will be able to see that the program is really
- running. However, the screen display invoked by the ``/T'' switch is not
- necessary for the operation of the Publisher, and when you have become
- accustomed to the operation of the program, you may decide to dispense
- with it.
-
- The next step to take (if you have not already done so) is to PUBLish
- this Tutorial, which is of course located on the RUBICON directory under
- the filename TUTORIAL.
-
- NOTE: This Tutorial is about 20 pages long, and takes substantial
- time<L->typically 30 to 45 minutes<L->to PUBLish. Having PUBLished the
- ``Samples'', you will have some idea of how long it takes your computer
- and printer to PUBLish one page: the Tutorial will take about 15 times
- as long. However, once you have started the process, it will proceed
- automatically without further instructions, provided that your printer's
- paper-handling mechanism is reliable and is loaded with enough paper for
- the job.
-
- To PUBLish the Tutorial:
-
- (a) Make sure your printer is ready and on line, with an adequate supply
- of paper.
-
- (b) Log on to the directory RUBICON on Drive C (if you are not already
- there) by entering the DOS command:
-
- CD C:\RUBICON [return]<QC>
-
- (c) enter the command:
-
- PUBL TUTORIAL /T [return]<QC>
-
- (d) Wait for the Tutorial to be printed out. <ai>(Remember to be patient!)<xi>
-
- <ql18pt>
- <ab><pt18>T.4<n>Text Files<pt12><xb><ql>
-
- The Publisher requires as input a plain ASCII text file, that is, a text
- file in standard ASCII format, without embedded control characters,
- right-justification, indentations or enhancements. Paragraphs should be
- separated from each other, and from headings and subheadings, by a
- single blank line, and trailing blank space characters at the end of
- lines or paragraphs should be avoided if possible.
-
- The first step in producing a published docoument is, therefore, to
- prepare the contents of the document in the form of a plain ASCII
- computer text file. This job is usually done by means of a ``word
- processor'' (text editing program). Most major word processors either
- produce text files in ASCII format in normal operation, or can be
- instructed to do so as an optional operating mode.
-
- To prepare text files for PUBLication by the Rubicon Publisher:
-
- 1. You should set your word processor to produce files in ASCII format,
- if it does not normally do so. (With some word processors, the necessary
- instruction is given at the time of saving the workfile to disk.)
-
- 2. Your word processor's right-justification feature (sometimes referred
- to simply as ``justification'') should be switched off (disabled).
-
- 3. Your word processor's built-in enhancements (bolding, underlining,
- alternate fonts, etc.) should <ai>not<xi> be used.
-
- 4. Tabular stops (``tabs'') should <ai>not<xi> be used. (The Publisher
- uses a different method for producing tables.)
-
- If you are uncertain about how to comply with these three requirements,
- please refer to your word processor's instruction manual.
-
- To save you the time and trouble of generating text files from scratch,
- we have provided two suitable plain text files for use in this Tutorial.
- They are located on the RUBICON directory, under the names TEXT.ONE and
- TEXT.TWO. In the Lessons which follow, you will learn how to use your
- word processor to ``tag'' these files for PUBLication.
-
- <ql18pt>
- <ab><pt18>T.5<N>Style Sheets and the <60>Include <.><.><.><62> Tag<pt12><xb><ql>
-
- The Publisher's ``include'' tag looks like this:
-
- <60>Include XXX<62><QC>
-
- where ``XXX'' is the name of some disk file. Its effect is to include
- the contents of the file ``XXX'' in your document file at the point
- where the ``Include'' tag appears. The included file may consist of
- instruction tags, or printable text, or both.
-
- A ``style sheet''is a special kind of file, consisting entirely of
- instruction tags, which provides a complete specification of the page
- layout and format to be used in PUBLishing the document.
-
- Style sheets for a selection of page formats are provided on your
- RUBICON directory as disk files, identified by the filename extension
- ``.sty''. The names of these files indicate the formats they represent.
- The first element in a style sheet filename is a number followed by the
- letter ``C'': this indicates the number of columns. The next element is
- a number followed by the letter ``P'': this indicates the size of print
- which will be used for the text, measured in ``points''. The final
- element is a 2-character abbreviation indicating the paper size: ``LT''
- for letter size, ``LG'' for legal size, ``A4'' for A4 size.
-
- Examples:
-
- <tab i=1 stop=0 justify=ql><qz>
- <tab i=2 stop=2in justify=ql><qz>
- <tab i=3 stop=6.5in justify=ql><qz>
- <HS>Filename<HT>Format<HE>
- <line thick=1pt><ql15pt>
- <HS>1C12PLT.STY<HT>Single column, 12-point type, letter-size paper<HE>
- <HS>2C10PLT.STY<HT>2 columns, 10-point type, letter-size paper<HE>
- <HS>3C10PLT.STY<HT>3 columns, 10-point type, letter-size paper<HE>
- <HS>4C8PLT.STY<HT> 4 columns, 8-point type, letter-size paper<HE>
- <line thick=1pt><ql15pt>
-
- <ql18pt>
- <ab><pt18>T.6<N>Lesson 1<pt12><xb><ql>
-
- In this Lesson, we will use the Publisher's ``Include'' tag and a
- standard ``style sheet'' to PUBLish a document in a standard style and
- format. The document we will PUBLish is contained in the file TEXT.ONE,
- and we will use the style sheet 2C12PLT.STY, which will set the text in
- 12-point Trajan type, 2 columns per page.
-
- <ab>STEP 1:<xb>
-
- Using your Word Processor (set up as described in Section T.4):
-
- (a) create a new version of the file C:\RUBICON\TEXT.ONE, amended as
- follows:
-
- Insert one new line at the beginning of the file, consisting of the
- instruction tag <60>INCLUDE 2C12PLT.STY<62> positioned at the left margin.
-
- (b) name the amended file LESSON.1; and
-
- (c) save it as an ASCII file on the directory C:\RUBICON.
-
- [The exact procedures for doing this will depend on what word processor
- you are using.]
-
- The beginning of the amended file LESSON.1 should look like this:
-
- <pt10><ib8em><leading line=11.5pt para=5pt><qz>
- <line thick=1pt><ql24pt>
- <60>INCLUDE 2C12PLT.STY<62><ql>
- At that time, in Kentucky (said the Hon. Mr. K--), the law was very
- strict against what are termed ``games of chance''. About a dozen of the
- boys were detected playing ``seven-up'' or ``old sledge'' for money, and
- the grand jury found a true bill against them. Jim Sturgis was retained
- <.><.><.><.><ql>
- <line thick=1pt><ql24pt>
- <pt12><ib><leading line=14pt para=7pt><qz>
-
- Note: The <60>INCLUDE ..<62> tag must be at the very beginning of the
- file. It must <ai>not<xi> be preceded by any blank lines or spaces.
-
- <ab>STEP 2:<xb>
-
- <ai>If your Publisher installation does not include the VGA Preview,
- omit this Step and proceed directly to Step 3.<xi>
-
- If your Publisher installation includes the VGA Preview, Preview your
- file LESSON.1, by doing the following:
-
- (a) Exit from your Word Processor and Log on to the directory RUBICON on
- Drive C (if you are not already there) by entering the DOS command:
-
- CD C:\RUBICON[return]<qc>
-
- (b) enter the command:
-
- PUBL LESSON.1 /P [return]<QC>
-
- (c) Wait for the Preview of LESSON.1 to appear on your screen.
- <ai>(Remember to be patient!)<xi>
-
- (d) The Preview displays a standard (8.5x11 in) document in 4
- overlapping views: Top Left, Top Right, Bottom Left, and Bottom Right.
- You are now looking at the Top Left view of Page 1 of your document
- LESSON.1. You will see that the document has been set up in Trajan
- (serif) type, in two columns. The Top Left view shows the top half of
- the first column, and a small part of the top half of the second
- column.
-
- (e) After you have examined the Top Left view, press the [CURSOR RIGHT]
- arrow key, and wait for the Top Right view of Page 1 to be displayed.
- <ai>(Remember to be patient!)<xi>
-
- (f) After you have examined the Top Right view, press the [CURSOR DOWN]
- arrow key, and wait for the Bottom Right view of Page 1 to be displayed.
- <ai>(Remember to be patient!)<xi>
-
- (g) After you have examined the Bottom Right view, press the
- [CURSOR<nb>LEFT] arrow key, and wait for the Bottom Left view of Page 1
- to be displayed. <ai>(Remember to be patient!)<xi>
-
- (h) You have now seen all 4 views of Page 1. If you wish, you can
- re-examine any view by using the cursor arrow keys to move around the
- page. <ai>(Remember to be patient!)<xi> The Publisher takes a few
- moments to move from one view to another: the new view does not appear
- instantly.
-
- (i) After you have finished examining Page 1, press the [PAGE DOWN] key
- to move to Page 2. Wait for the Preview of Page 2 to appear on your
- screen. <ai>(Remember to be patient!)<xi>
-
- (j) In a few moments, the Top Left view of Page 2 of LESSON.1 will
- appear. (You will get the Top Left view of Page 2, no matter which view
- of Page 1 was on your screen when you pressed the [PAGE DOWN] key.)
-
- (k) Repeat (e), (f) and (g) to examine the other 3 views of Page 2.
-
- (l) After you have finished examining Page 2, press the [PAGE DOWN] key.
- Since Page 2 is the last page of your document LESSON.1, pressing [PAGE
- DOWN] will conclude the Preview session, and return you to the DOS
- prompt, ``C<pi62>''.
-
- <ab>STEP 3:<xb>
-
- PUBLish your file LESSON.1, by doing the following:
-
- (a) Make sure your printer is ready and on line.
-
- (b) If you are still in your Word Processor, exit from it. Log on to the
- directory RUBICON on Drive C (if you are not already there) by entering
- the DOS command:
-
- CD C:\RUBICON[return]<qc>
-
- (c) enter the command:
-
- PUBL LESSON.1 /T [return]<QC>
-
- (d) Wait for LESSON.1 to be printed out, and examine the result.
- <ai>(Remember to be patient!)<xi> Save the printed document for future
- reference.
-
- <ql18pt>
- <ab><pt18>T.7<N>Lesson 2<pt12><xb><ql>
-
- In this Lesson, we will rePUBLish the same document used in Lesson 1, in
- two different formats by using different style sheets in place of the
- style sheet 2C12PLT.STY, which we used in Lesson 1.
-
- <ab>STEP 1:<xb>
-
- Using your Word Processor (set up as described in Section T.4):
-
- (a) amend your file C:\RUBICON\LESSON.1 by changing the instruction tag
- at the beginning of the file to read:
-
- <60>INCLUDE 1C12PLT.STY<62>
-
- [That is, change the name of the style sheet being included to
- ``1C12PLT.STY''.]
-
- (b) Rename the file ``LESSON.2A'', and save it as an ASCII file on the
- directory C:\RUBICON.
-
- The beginning of the file LESSON.2A should now look like this:
-
- <pt10><ib8em><leading line=11.5pt para=5pt><qz>
- <line thick=1pt><ql24pt>
- <60>INCLUDE 1C12PLT.STY<62><ql>
- At that time, in Kentucky (said the Hon. Mr. K--), the law was very
- strict against what are termed ``games of chance''. About a dozen of the
- boys were detected playing ``seven-up'' or ``old sledge'' for money, and
- the grand jury found a true bill against them. Jim Sturgis was retained
- <.><.><.><.><ql>
- <line thick=1pt><ql24pt>
- <pt12><ib><leading line=14pt para=7pt><qz>
-
- Note: The <60>INCLUDE ..<62> tag must be at the very beginning of the file. It
- must NOT be preceded by any blank lines or spaces.
-
- <ab>STEP 2:<xb>
-
- <ai>If your Publisher installation does not include the VGA Preview,
- omit this Step and proceed directly to Step 3.<xi>
-
- If your Publisher installation includes the VGA Preview, Preview the new
- file LESSON.2A, by doing the following:
-
- (a) Exit from your Word Processor and Log on to the directory RUBICON on
- Drive C (if you are not already there) by entering the DOS command:
-
- CD C:\RUBICON[return]<qc>
-
- (b) enter the command:
-
- PUBL LESSON.2A /P [return]<QC>
-
- (c) Wait for the Preview of LESSON.2A to appear on your screen.
- <ai>(Remember to be patient!)<xi>
-
- (d) The Preview displays a standard (8.5x11 in) document in 4
- overlapping views: Top Left, Top Right, Bottom Left, and Bottom Right.
- You are now looking at the Top Left view of Page 1 of your document
- LESSON.2A. You will see that the document has been set up in Trajan
- (serif) type, in a single column, the full width of the page.
-
- (e) After you have examined the Top Left view, press the [CURSOR RIGHT]
- arrow key, and wait for the Top Right view of Page 1 to be displayed.
- <ai>(Remember to be patient!)<xi>
-
- (f) After you have examined the Top Right view, press the [CURSOR DOWN]
- arrow key, and wait for the Bottom Right view of Page 1 to be displayed.
- <ai>(Remember to be patient!)<xi>
-
- (g) After you have examined the Bottom Right view, press the
- [CURSOR<nb>LEFT] arrow key, and wait for the Bottom Left view of Page 1
- to be displayed. <ai>(Remember to be patient!)<xi>
-
- (h) You have now seen all 4 views of Page 1. If you wish, you can
- re-examine any view by using the cursor arrow keys to move around the
- page. <ai>(Remember to be patient!)<xi> The Publisher takes a few
- moments to move from one view to another: the new view does not appear
- instantly.
-
- (i) After you have finished examining Page 1, press the [PAGE DOWN] key
- to move to Page 2. Wait for the Preview of Page 2 to appear on your
- screen. <ai>(Remember to be patient!)<xi>
-
- (j) In a few moments, the Top Left view of Page 2 of LESSON.2A will
- appear. (You will get the Top Left view of Page 2, no matter which view
- of Page 1 was on your screen when you pressed the [PAGE DOWN] key.)
-
- (k) Repeat (e), (f) and (g) to examine the other 3 views of Page 2.
-
- (l) After you have finished examining Page 2, press the [PAGE DOWN] key.
- Since Page 2 is the last page of your document LESSON.2A, pressing [PAGE
- DOWN] will conclude the Preview session, and return you to the DOS
- prompt, ``C<pi62>''.
-
- <ab>STEP 3:<xb>
-
- PUBLish LESSON.2A, by doing the following:
-
- (a) Make sure your printer is ready and on line.
-
- (b) If you are still in your Word Processor, exit from it. Log on to the
- directory RUBICON on Drive C (if you are not already there) by entering
- the DOS command:
-
- CD C:\RUBICON[return]<qc>
-
- (c) enter the command:
-
- PUBL LESSON.2A /T [return]<QC>
-
- (d) Wait for LESSON.2A to be printed out, and examine the result.
- <ai>(Remember to be patient!)<xi> Save the printed document for future
- reference.
-
- <ab>STEP 4:<xb>
-
- Using your Word Processor (set up as described in Section T.4):
-
- (a) amend your file C:\RUBICON\LESSON.2A by changing the instruction tag
- at the beginning of the file to read:
-
- <60>INCLUDE 3C10PLT.STY<62>
-
- [That is, change the name of the style sheet being included to
- ``3C10PLT.STY''.]
-
- (b) Rename the file ``LESSON.2B'', and save it as an ASCII file on the
- directory C:\RUBICON.
-
- The beginning of the amended file LESSON.2B should now look like this:
-
- <pt10><ib8em><leading line=11.5pt para=5pt><qz>
- <line thick=1pt><ql24pt>
- <60>INCLUDE 3C10PLT.STY<62><ql>
- At that time, in Kentucky (said the Hon. Mr. K--), the law was very
- strict against what are termed ``games of chance''. About a dozen of the
- boys were detected playing ``seven-up'' or ``old sledge'' for money, and
- the grand jury found a true bill against them. Jim Sturgis was retained
- <.><.><.><.><ql>
- <line thick=1pt><ql24pt>
- <pt12><ib><leading line=14pt para=7pt><qz>
-
- Note: The <60>INCLUDE ..<62> tag must be at the very beginning of the file. It
- must NOT be preceded by any blank lines or spaces.
-
- <ab>STEP 5:<xb>
-
- <ai>If your Publisher installation does not include the VGA Preview,
- omit this Step and proceed directly to Step 6.<xi>
-
- If your Publisher installation includes the VGA Preview, Preview the new
- file LESSON.2B, by using the procedure described in Step 2 of this lesson.
- [The command this time will of course be: PUBL LESSON.2B /P.]
-
- <ab>STEP 6:<xb>
-
- PUBLish LESSON.2B, by usinmg the procedure described in Step 3 of this
- lesson. [The command this time will of course be: PUBL LESSON.2B /T.]
-
- <ab>STEP 7:<xb>
-
- Compare the PUBLished versions of the document produced in this lesson
- with each other, and with the version produced in Lesson 1.
-
- <ql18pt>
- <ab><pt18>T.8<N>Lesson 3<pt12><xb><ql>
-
- In this lesson, we will use a Publisher instruction tag to modify the
- document format specified by a Style Sheet.
-
- Your file LESSON.2B included the Style Sheet 3C10PLT.STY; that is, it
- was printed in Trajan 10-point type, in 3 columns. Looking at your
- printed copy, you will see that the text <ai>almost<xi> fits on one
- page, but not quite. To make the text fit on one page, we will make a
- small reduction in the line spacing, known technically as the
- ``leading'' (pronounced ``ledding''). The <ai>minimum<xi> leading for
- 10-point type is 10 points (ten seventy-seconds of an inch), but a
- printed page looks less crowded, and is easier to read, if a leading
- larger than the minimum is used.
-
- Leading is controlled by the instruction tag <pi60>leading line=x
- para=y<pi62> where x is the line leading, and y is the extra leading
- inserted between paragraphs. The Style Sheet 3C10PLT.STY prescribes a
- line leading of ``12pt'' (12 points) and a paragraph leading of ``5pt''
- (5 points). We are going to reduce each of these by one point, as
- follows:
-
- <ab>STEP 1:<xb>
-
- Using your Word Processor (set up as described in Section T.4):
-
- (a) amend your file C:\RUBICON\LESSON.2B by inserting a new line
- <ai>immediately below<xi> the instruction tag ``<60>INCLUDE
- 3C10PLT.STY<62>''. The new line to be inserted is:
-
- <pi60>leading line=11pt para=4pt<pi62><pi60>qz<pi62>
-
- [The tag <pi60>qz<pi62> is a punctuation tag which tells the Publisher
- that the line of instructions has ended, without creating a blank line
- in the printed file.]
-
- (b) Rename the file ``LESSON.3'' and save it as an ASCII file on the
- directory C:\RUBICON.
-
- The beginning of the new file LESSON.3 should now look like this:
-
- <pt10><ib8em><leading line=11.5pt para=5pt><qz>
- <line thick=1pt><ql24pt>
- <60>INCLUDE 3C10PLT.STY<62><ql>
- <pi60>leading line=11pt para=4pt<pi62><pi60>qz<pi62><ql>
- At that time, in Kentucky (said the Hon. Mr. K--), the law was very
- strict against what are termed ``games of chance''. About a dozen of the
- boys were detected playing ``seven-up'' or ``old sledge'' for money, and
- the grand jury found a true bill against them. Jim Sturgis was retained
- <.><.><.><.><ql>
- <line thick=1pt><ql24pt>
- <pt12><ib><leading line=14pt para=7pt><qz>
-
- Note: The new line should be <ai>exactly<xi> as given above.
-
- <ab>STEP 2:<xb>
-
- <ai>If your Publisher installation does not include the VGA Preview,
- omit this Step and proceed directly to Step 3.<xi>
-
- If your Publisher installation includes the VGA Preview, Preview the new
- file LESSON.3. (Refer back to Step 2 of Lesson 2, in Section T.7, if you
- need to.) Note: When you press [PAGE DOWN] after previewing Page 1, the
- Preview session will terminate, and you will be returned to the DOS
- prompt, ``C<pi62>''. Since the document now consists of a single page,
- there is no ``Page 2'' to be previewed.
-
- <ab>STEP 3:<xb>
-
- PUBLish LESSON.3. (Refer back to Step 3 of Lesson 2,
- in Section T.7, if you need to.)
-
- <ql18pt>
- <ab><pt18>T.9<N>Lesson 4<pt12><xb><ql>
-
- In this lesson, we will use the Publisher ``header'' instruction to
- insert a heading at the beginning of the file LESSON.3. The heading we
- will insert is the title of the story, ``Luck versus Science'', and we
- will insert it in large 24-point bold type. We will also use the
- ``Footer'' instruction to cancel page numbering, which is not needed for
- a 1-page document.
-
- <ab>STEP 1:<xb>
-
- Using your Word Processor (set up as described in Section T.4):
-
- (a) amend your file C:\RUBICON\LESSON.3 by inserting 7 new lines
- <ai>immediately below<xi> the instruction line<ql>
- ``<pi60>leading line=11pt para=4pt<pi62><pi60>qz<pi62>''
-
- The new lines to be inserted are:
-
- <60>header<62><ql>
- <60>margin left=0.75in right=7.75in<62><60>qz<62><ql>
- <60>Trajan24b<62>LUCK versus SCIENCE<60>Trajan12m<62><60>qc<62><ql>
- <60>end<62><ql>
- <60>footer<62><ql>
- <ql>
- <60>end<62><ql>
- <ql>
-
- (b) Rename the file ``LESSON.4'', and save it as an ASCII file on the
- directory C:\RUBICON.
-
- The beginning of the new file LESSON.4 should now look like this:
-
- <pt10><ib8em><leading line=11.5pt para=5pt><qz>
- <line thick=1pt><ql24pt>
- <60>INCLUDE 3C10PLT.STY<62><ql>
- <pi60>leading line=11pt para=4pt<pi62><pi60>qz<pi62><ql>
- <60>header<62><ql>
- <60>margin left=0.75in right=7.75in<62><60>qz<62><ql>
- <60>Trajan24b<62>LUCK versus SCIENCE<60>Trajan12m<62><60>qc<62><ql>
- <60>end<62><ql>
- <60>footer<62><ql>
- <ql>
- <60>end<62><ql>
- At that time, in Kentucky (said the Hon. Mr. K--), the law was very
- strict against what are termed ``games of chance''. About a dozen of the
- boys were detected playing ``seven-up'' or ``old sledge'' for money, and
- the grand jury found a true bill against them. Jim Sturgis was retained
- <.><.><.><.><ql>
- <line thick=1pt><ql24pt>
- <pt12><ib><leading line=14pt para=7pt><qz>
-
- Note: The new lines should be <ai>exactly<xi> as given above. There must
- be a blank line between the lines ``<60>footer<62>'' and
- ``<60>end<62>'', as shown, and no other blank lines between the
- beginning of the file and the first line of actual text.
-
- <ab>STEP 2:<xb>
-
- <ai>If your Publisher installation does not include the VGA Preview,
- omit this Step and proceed directly to Step 3.<xi>
-
- If your Publisher installation includes the VGA Preview, Preview the new
- file LESSON.4. (Refer back to Step 2 of Lesson 2, in Section T.7, if you
- need to.) Note: When you press [PAGE DOWN] after previewing Page 1, the
- Preview session will terminate, and you will be returned to the DOS
- prompt, ``C<pi62>''. Since the document now consists of a single page,
- there is no ``Page 2'' to be previewed.
-
- <ab>STEP 3:<xb>
-
- PUBLish LESSON.4. (Refer back to Step 3 of Lesson 2, in Section T.7, if
- you need to.)<ql>
- <il3em><pt10><leading line=11pt para=5pt><qz>
-
- [The ``header'' and ``footer'' instructions are used to define running
- headers and footers. A ``header'', once defined, will appear at the top
- of every new page of the document, starting at the first page break
- after the instruction, until a new header instruction is encountered. To
- make a header appear on the first page of the document, you must define
- it at the beginning of the file, before the first page begins, that is,
- before any printable text. Similarly, a ``footer'', once defined, will
- appear at the bottom of every new page of the document, starting at the
- first page break after the instruction, until a new footer instruction
- is encountered. To make a footer appear on the first page of the
- document, you must define somewhere before the end of the first page.
-
- In this lesson, we have used a ``header'' instruction at the beginning
- of the file to define a heading which appears on the first (and only)
- page of the document.
-
- The standard Style Sheets all include a definition of a standard footer
- consisting of the page number, printed at the center of the page.
- (Inside a header or footer definition, the page number is represented by
- the tag <60>PN<62>.) In this lesson, we have cancelled this by using a
- ``footer'' instruction to define a ``blank'' footer, that is, a footer
- containing nothing.]<ql>
- <pt12><il><leading line=14pt para=7pt><qz>
-
- <ql18pt>
- <ab><pt18>T.10<N>Lesson 5<pt12><xb><ql>
-
- In this lesson, we will use some Publisher instruction tags to add some
- ``enhancements'' to the file LESSON.4 which will give the
- document a more professional appearance. Looking at the printed
- copy of LESSON.4, you will see that there are 5 places where a pair of
- hyphens, ``--'', has been used to represent a dash, ``<L->''. We will
- replace these hyphen pairs with single dashes, using the tag
- ``<60>L-<62>'', which specifies a ``long dash'' (three-quarters of an em
- long). We will also add some italics, and we will right-justify the last
- line of the document, which identifies the author and date of the story;
- that is, move it over so that it ends at the right-hand side of the
- column.
-
- <ab>STEP 1:<xb>
-
- Using your Word Processor (set up as described in Section T.4), access
- the file LESSON.4, and:
-
- (a) Locate the 5 occurrences of ``--'', and replace each of them with
- ``<60>L-<62>''. Your word processor probably has a ``search and
- replace'' utility which can perform this task easily.
-
- Example: The first line of text in the file should now read:
-
- <pt10><leading line=11.5pt para=5pt><qz>
- At that time, in Kentucky (said the Hon. Mr. K<60>L-<62>), the law was
- very<qc>
- <pt12><leading line=14pt para=7pt><qz>
-
- (b) Locate the word ``proven'' in the text. (It is found a few lines
- from the end of the second paragraph). Italicize it by inserting the tag
- ``<60>ai<62>'' in front of it, and the tag ``<60>xi<62>'' after it.
-
- The line of text in which the word ``proven'' appears should now look
- like this:
-
- <pt10><leading line=11.5pt para=5pt><qz>
- it was <60>ai<62>proven<60>xi<62> that it was a game of chance. Judge
- and counsel<qc>
- <pt12><leading line=14pt para=7pt><qz>
-
- (c) Move to the last line of the file, and amend it by inserting the tag
- ``<60>ai<62>'' at the beginning of the line, and the sequence of tags
- ``<60>xi<62><60>qr<62>'' at the end of the line, like this:
-
- <pt10><leading line=11.5pt para=5pt><qz>
- <60>ai<62><60>L-<62>Mark Twain (1870)<60>xi<62><60>qr<62><qc>
- <pt12><leading line=14pt para=7pt><qz>
-
- The beginning and ending of the file LESSON.4 should now look like this:
-
- <pt10><ib8em><leading line=11.5pt para=5pt><qz>
- <line thick=1pt><ql24pt>
- <60>INCLUDE 3C10PLT.STY<62><ql>
- <pi60>leading line=11pt para=4pt<pi62><pi60>qz<pi62><ql>
- <60>header<62><ql>
- <60>margin left=0.75in right=7.75in<62><60>qz<62><ql>
- <60>Trajan24b<62>LUCK versus SCIENCE<60>Trajan12m<62><60>qc<62><ql>
- <60>end<62><ql>
- <60>footer<62><ql>
- <ql>
- <60>end<62><ql>
- At that time, in Kentucky (said the Hon. Mr. K<60>L-<62>), the law was very
- strict against what are termed ``games of chance''. About a dozen of the
- boys were detected playing ``seven-up'' or ``old sledge'' for money, and
- the grand jury found a true bill against them. Jim Sturgis was retained
- <.><.><.><.><ql>
-
- *<M>*<M>*<M>*<M>*<qc>
-
- ``That is the way that seven-up came to be set apart and particularized
- in the statute-books of Kentucky as being a game not of chance but of
- science, and therefore not punishable under the law,'' said Mr.
- K<60>L-<62>. ``That verdict is of record, and holds good to this day.''
-
- <60>ai<62><60>L-<62>Mark Twain (1870)<60>xi<62><60>qr<62><ql>
- <line thick=1pt><ql24pt>
- <pt12><ib><leading line=14pt para=7pt><qz>
-
- (d) Rename the file ``LESSON.5'' and save it as an ASCII file on the
- directory C:\RUBICON.
-
- <ab>STEP 2:<xb>
-
- <ai>If your Publisher installation does not include the VGA Preview,
- omit this Step and proceed directly to Step 3.<xi>
-
- If your Publisher installation includes the VGA Preview, Preview the new
- file LESSON.5. (Refer back to Step 2 of Lesson 2, in Section T.7, if you
- need to.) Note: When you press [PAGE DOWN] after previewing Page 1, the
- Preview session will terminate, and you will be returned to the DOS
- prompt, ``C<pi62>''. Since the document now consists of a single page,
- there is no ``Page 2'' to be previewed.
-
- <ab>STEP 3:<xb>
-
- PUBLish LESSON.5. (Refer back to Step 3 of Lesson 2, in Section T.7, if
- you need to.)
-
- <ql18pt>
- <ab><pt18>T.11<N>Lesson 6<pt12><xb><ql>
-
- In this lesson we will be using the prepared files TEXT.TWO and TAB.ONE,
- from your Rubicon directory, to demonstrate the basic procedures for
- defining headers, for using enhancements, and for presenting information
- in tabular form.
-
- <ab>STEP 1:<xb>
-
- Use your word processor, or the DOS command ``TYPE <ai>filename<xi>'',
- to display the file TAB.ONE on your screen. This file contains a series
- of instruction tags which set up a table 5 inches wide, consisting of 4
- columns, defined by 5 tab stops spaced at equal intervals of 1.25
- inches. Each tab stop is defined by a tag:<ql>
- <60>tab i= stop= justify= <62><qc>
- where ``i= ''defines the tab stop number; ``stop= '' specifies the
- distance of the tab stop from the left-hand edge of the table; and
- ``justify= '' specifies the method of justification to be used inside
- the tab column: ``ql'' for left justification, ``qr'' for right
- justification, or ``qc'' for center justification. In this example,
- center justification is being used.
-
- This file is ``included'' at 2 locations in the file TEXT.TWO, to
- present information in the form of a table. When you Preview or PUBLish
- this text file (Steps 3 and 4, below) you will see the form of table
- which results from these instructions.
-
- <ai>Leave this file<xi> TAB.ONE <ai>unchanged.<xi>
-
- <ab>STEP 2:<xb>
-
- Using your Word Processor (set up as described in Section T.4), access
- the file C:\RUBICON\TEXT.TWO, and:
-
- (a) insert the following 8 new lines at the very beginning of the file,
- starting at line 1:
-
- <60>include 1c12plt.sty<62><ql>
- <60>header<62><ql>
- <60>margin left=0.75in right=7.75in<62><60>qz<62><ql>
- <60>Renner24b<62>PAGE LAYOUT GUIDELINES<60>Trajan12m<62><60>qc<62><ql>
- <60>end<62><ql>
- <60>footer<62><ql>
- <ql>
- <60>end<62><ql>
-
- The first new line adopts the style sheet 1C12PLT.STY for printing the
- document in Trajan 12-point type, in one column. The next 4 lines place
- the heading ``PAGE LAYOUT GUIDELINES'' centered in the header space at
- the top of the first page, printed in Renner 24-point bold type, by
- defining it as the initial running header for the document. The next 3
- lines cancel the standard page-numbering footer defined by the style
- sheet, by defining a blank footer.
-
- (b) Amend the first line of text, ``Column Layouts'', by inserting the
- tag ``<60>Renner14b<62>'' at the beginning of the line, and the tag
- ``<60>Trajan12m<62>'' at the end of the line, so that the whole line
- looks like this:<ql>
- ``<60>Renner14b<62>Column Layouts<60>Trajan12m<62>''
-
- ``<60>Renner14b<62>'' is a font tag, specifying that the text following
- it is to be printed in the Renner typeface, in 14-point bold type.
- Similarly, ``<60>Trajan12m<62>'' specifies that the text following it is
- to be printed in the Trajan typeface, in 12-point medium type.
-
- (c) Immediately below the line amended in (b), insert a blank line, then
- insert the following 5 new lines:<ql>
-
- <60>header<62><ql>
- <60>margin left=0.75in right=7.75in<62><60>qz<62><ql>
- <60>Renner12i<62>Page Layout Guidelines<60>qz<62><ql>
- Page <60>pn<62><60>Trajan12m<62><60>qr<62><ql>
- <60>end<62><ql>
-
- The last of these new lines should be separated from the next line of
- text by a blank line.
-
- The beginning of the text file should now look like this:
-
- <pt10><ib8em><leading line=11.5pt para=5pt><qz>
- <line thick=1pt><ql24pt>
- <60>include 1c12plt.sty<62><ql>
- <60>header<62><ql>
- <60>margin left=0.75in right=7.75in<62><60>qz<62><ql>
- <60>Renner24b<62>PAGE LAYOUT GUIDELINES<60>Trajan12m<62><60>qc<62><ql>
- <60>end<62><ql>
- <60>footer<62><ql>
- <ql>
- <60>end<62><ql>
- <60>Renner14b<62>Column Layouts<60>Trajan12m<62><ql>
-
- <60>header<62><ql>
- <60>margin left=0.75in right=7.75in<62><60>qz<62><ql>
- <60>Renner12i<62>Page Layout Guidelines<60>qz<62><ql>
- Page <60>pn<62><60>Trajan12m<62><60>qr<62><ql>
- <60>end<62><ql>
-
- For a page interior 7 inches wide, the following column layouts may
- be considered:
-
- Arrangement 1. <60>column measure=7.0in<62> or <60>column count=1<62>.
- One column 7 inches wide fills the page.<ql>
- <.><.><.><.><ql>
- <line thick=1pt><ql24pt>
- <pt12><ib><leading line=14pt para=7pt><qz>
-
- The newly-added lines define a new running header for the document.
- Because the new header definition is located <ai>after the first line of
- printable text,<xi> but <ai>before the end<xi> of the first page of the
- document, the new header will not appear on the first page, but will
- appear on all subsequent pages. The new header will be printed in Renner
- 12-point italic type, and consists of the title ``Page Layout
- Guidelines'', which will appear at the left of the page, and the word
- ``Page'' followed by the page number, which will appear at the right of
- the page.
-
- (d) Locate the heading ``Leading (Line Spacing)'', which appears on a
- line by itself, about 80 lines from the beginning of the file. Amend
- this line by inserting the tag ``<60>Renner14b<62>'' at the beginning of
- the line, and the tag ``<60>Trajan12m<62>'' at the end of the line, so
- that the whole line looks like this:<ql>
- ``<60>Renner14b<62>Leading (Line Spacing)<60>Trajan12m<62>''
-
- This will cause the heading to be printed in Renner 14-point bold type.
-
- (e) Locate the heading ``General Comments'', which appears on a
- line by itself, about 144 lines from the beginning of the file. Amend
- this line by inserting the tag ``<60>Renner14b<62>'' at the beginning of
- the line, and the tag ``<60>Trajan12m<62>'' at the end of the line, so
- that the whole line looks like this:<ql>
- ``<60>Renner14b<62>General Comments<60>Trajan12m<62>''
-
- This will cause the heading to be printed in Renner 14-point bold type.
-
- (f) Locate the first sentence in the last paragraph of the document
- (about 167 lines from the beginning),
- which reads:<ql>
- ``Finally, print enhancements<60>L-<62>bold face, italics, and
- underlining<60>L-<62>should be used sparingly.''
-
- Amend ``bold face,'' to
- ``<60>ab<62>bold face,<60>xb<62>''.
-
- Amend ``italics,'' to
- ``<60>ai<62>italics,<60>xi<62>''.
-
- Amend ``underlining'' to
- ``<60>au<62>underlining<60>xu<62>''.
-
- The whole sentence, as amended, should read:<ql>
-
- ``Finally, print enhancements<60>L-<62><60>ab<62>bold face,<60>xb<62>
- <60>ai<62>italics,<60>xi<62> and
- <60>au<62>underlining<60>xu<62><60>L-<62>should be used sparingly.''
-
- (g) Name the amended text file LESSON.6 and save it as an ASCII file on
- the directory C:\RUBICON.
-
- <ab>STEP 3:<xb>
-
- <ai>If your Publisher installation does not include the VGA Preview,
- omit this Step and proceed directly to Step 4.<xi>
-
- If your Publisher installation includes the VGA Preview, Preview the
- file LESSON.6. (Refer back to Step 2 of Lesson 2, in Section T.7, if you
- need to.) Note: This document is 3 pages in length. When you press [PAGE
- DOWN] after previewing Page 3, the Preview session will terminate, and
- you will be returned to the DOS prompt, ``C<pi62>''.
-
- <ab>STEP 4:<xb>
-
- PUBLish the file LESSON.6. (Refer back to Step 3 of Lesson 2,
- in Section T.7, if you need to.)
-
- <ab>STEP 5:<xb>
-
- Examine the printed document, with particular attention to the headings,
- running header, and tables.
-
- The document contains useful guidelines for publishing text files: save
- it for future reference.
-
- <ql18pt>
- <ab><pt18>T.12<N>Publishing Your Own Documents<pt12><xb><ql>
-
- Now that you have completed the ``six easy lessons'', you can use the
- Publisher to PUBLish your own documents in a wide variety of styles and
- formats, and with various enhancements. In fact, you can do a lot of
- useful PUBLishing without learning anything more about the Publisher
- than you know right now.
-
- Of course, this Tutorial has covered only the basics. The Publisher has
- more than 100 operational features, far too many to be included in a
- tutorial of reasonable length.
-
- The <ai>best<xi> source of information about the additional features of
- the Rubicon Publisher is the printed <ab>Reference Manual<xb>, which is
- included in the Commercial Edition of the Publisher, supplied to all
- registered users. The Reference Manual includes a Quick Reference Guide
- and an alphabetical index, which makes it easy to look up information
- about the specific features you want to use, as and when you need them.
-
- If you have obtained the Publisher as Shareware, and have not yet
- registered and paid your licence fee, you can learn about the Publisher's
- additional features from the <ab>Concise Manual<xb>, which is found in
- your RUBICON directory in files MANUAL.1 <.><.><.> MANUAL.8. You can
- print out a ``hard copy'' of the Concise Manual by printing these files,
- using your word processor or the DOS ``PRINT'' utility. They can also be
- displayed on your screen, using your word processor, or the DOS command:
- ``TYPE <ai>filename<xi> |MORE''. The file SAMPLE_4, which you have
- already PUBLished, is the table of contents for the Concise Manual, and
- the MANUAL file numbers correspond to the section numbers of the Manual:
- Section 3 of the Concise Manual is found in file MANUAL.3, and so on.
-
- The PUBLished ``Samples'' and Tutorial are also good sources of
- information, since they include various enhancements and special
- effects, and you can find out how these were produced by examining the
- text files from which the Samples and Tutorial were PUBLished. The text
- files can be displayed on your screen, using your word processor, or the
- DOS command: ``TYPE <ai>filename<xi> |MORE''. If desired, you can print
- hard copies of them using your word processor or the DOS ``PRINT''
- utility, for detailed comparison with the PUBLished documents.
-
- <il3em><pt10><leading line=11pt para=5pt><qz>
- [Note: The text file for this Tutorial may look confusing at first. As
- you know, instruction tags are separated from the printable text by
- chevron brackets, ``<60>'' and ``<62>'', and the Publisher treats
- <ab>anything<xb> enclosed in such brackets as an instruction, not as
- printable text. This causes a minor problem when you actually want to
- print a chevron bracket ``<60>'' or ``<62>'' as part of the text.
-
- To print ``<60>'' you must insert the tag ``<60>60<62>'' at the desired
- location in the text: to print ``<62>'' you must insert the tag
- ``<60>62<62>''. (If you are an experienced computer user, you may
- recognize ``60'' and ``62'' as the ASCII numbers for the characters
- ``<60>'' and ``<62>''.) Since the chevron brackets ``<60>'' and ``<62>''
- are used very frequently in the Tutorial, the tags ``<60>60<62>'' and
- ``<60>62<62>'' appear very frequently in the TUTORIAL text file, giving
- it a somewhat cluttered and confusing appearance.]<ql>
- <pt12><il><leading line=14pt para=7pt><qz>
-
- The standard Style Sheets on your RUBICON directory provide a good
- selection of page styles, but the Publisher is not limited to these. You
- can use any page style that will fit inside the printable zone of your
- page. (Printable zones are explained in Section 7.1.2 of the Concise
- Manual.) To use a different style, you can include a standard style
- sheet at the beginning of your file, followed by one or more over-riding
- instruction tags, as was done in Lesson 3. You can also create your own
- Style Sheets: see Section 8 of the Concise Manual.
-
- <ql18pt>
- <ab><pt18>T.13<N>Solving Problems<pt12><xb><ql>
-
- If the Publisher fails to Preview or PUBLish your text file, or appears
- to be ignoring your instructions, or acting on instructions you did not
- intend to give it, the problem can almost invariably be traced to some
- error in your text file, or in some file included therein. When trying
- to locate and correct such errors, you must bear in mind that all
- instructions to the Publisher must be letter-perfect, using the exact
- syntax shown in the Manual or Tutorial.
-
- Some common errors to look for:<ql>
- <ih2em><qz>
-
- Missing chevron bracket, particularly in a line containing several
- instruction tags. Each individual tag must start with ``<60>'' and end
- with ``<62>''.
-
- Blank spaces in the wrong place. Instruction tags must appear exactly as
- shown in the Manual, without any extra blank spaces, and in a line of
- instructions containing several tags, there should be no blank spaces
- between tags. Example:<ql>
- <M>WRONG: <60>margin<nb>left=<n>1in<n>right=<n>7.5in<62><n><60>qz<62><ql>
- <M>RIGHT: <60>margin<nb>left=1in<nb>right=7.5in<62><60>qz<62><ql>
-
- Unit of Measurement missing. When specifying a measurement or distance,
- you <ai>must<xi> specify the unit you are using. Example:<ql>
- <M>WRONG: <60>margin<nb>left=1<nb>right=7.5<62><60>qz<62><ql>
- <M>RIGHT: <60>margin<nb>left=1in<nb>right=7.5in<62><60>qz<62><ql>
- <M>RIGHT: <60>margin<nb>left=2.54cm<nb>right=19.05cm<62><60>qz<62><ql>
-
- Margin locations wrong, especially right, bottom and footer margins.
- Remember that <ai>all<xi> margin locations are measured from the <ai>top
- left corner<xi> of the page. If you want a 1-inch margin at the right
- side of a standard 8.5x11-inch page, the correct value for the right margin
- is ``7.5in'', <ai>not<xi> ``1in''. Example: 1-inch margins all
- around:<ql>
- <60>margin<nb>left=1in<nb>right=7.5in<nb>top=1in<nb>bottom=10.0in<62><60>qz<62><qc>
-
- Line of instruction tags not ended by ``quad'' tag. Generally, a line
- consisting only of instruction tags (other than a ``directive'') must
- end with a ``quad'' (punctuation) tag such as ``<60>qz<62>'': see
- Section 2.5 of the manual.
-
- Line break tag missing. The Publisher inserts line breaks automatically
- when it reaches the right-hand edge of the column, and when it reaches
- the end of a paragraph (indicated by a blank line or a ``<60>qp<62>''
- tag). If a line break is needed anywhere else, you must use a ``quad''
- tag, such as ``<60>ql<62>''. See Section 4.1 of the Manual.
-
- Chevron bracket (``<60>'' or ``<62>'') which is not part of an
- instruction tag. In text files to be PUBLished, chevron brackets should
- be used <ai>only<xi> to designate instruction tags, and nowhere else. To
- print chevron brackets as part of the text, you must use the tags
- ``<60>60<62>'' for ``<60>'' and ``<60>62<62>'' for ``<62>''.
-
- Nested ``Include'' instructions. The file named in an
- ``<60>include<nb><.><.><.><62>'' tag may consist of instructions,
- printable text, or both, but must <ai>not<xi> contain any further
- ``<60>include<nb><.><.><.><62>'' tags.
-
- Column too narrow. The defined column width is so narrow that individual
- words are too long to fit in it.
-
- Text is being clipped at one or more edges of page. This happens when
- one or more of the margin settings is incompatible with the paper size
- and printer model. The margins (including header and/or footer drops, if
- there are headers and/or footers) must be chosen so that all text to be
- printed, including any headers and footers, falls inside the printable
- zone. See Section 7.1 of the Manual.
-
- <ib><ih><ql18pt>
- <ab><pt18>T.14<N>Conclusion<pt12><xb><ql>
-
- We hope that you will find the Rubicon Publisher both useful and
- enjoyable. We believe that it out-performs all other products in its
- price class, and that its output compares favorably with the most
- expensive (and complicated) desktop publishers.
-
- Of course, no software product is ever perfect: improved future versions
- of the Rubicon Publisher are already in the planning stages, and input
- from our customers is always welcome. If you have suggestions<L->changes
- which would make the Publisher easier to use, new features or
- capabilities which you would like to have, additional hardware you would
- like the Publisher to support<L->please let us know.
-
- <ai>Please remember<xi> that use of the Publisher for purposes other than
- evaluation is against the law, unless you purchase a user's licence.
- When registering, please use one of the self-publishing Registration and
- Order forms which appear on the Rubicon directory when you install the
- software:
-
- <il0.5in><qz>
- *<N>In the U.S.A., use REGFORM.US<ql>
- *<N>In the U.K and Europe, use REGFORM.UK<ql>
- *<N>In Australia and New Zealand, use REGFORM.ANZ<ql>
- *<N>In Canada, use REGFORM.CAN<ql>
- *<N>In any other location, use REGFORM.FOR<ql>
-
- <il><qz>
- The current licence fees for the various versions of the Publisher are
- specified in these forms.
-
- <ai>Please note our mailing address for Registrations:<xi>
-
- <il1.0in><qz>
- RUBICON COMPUTER LABS INC.<ql>
- P.O. Box 336<ql>
- Chelsea, Quebec, Canada<ql>
- J0X 1N0<ql>
-
- <il><qz>
- When you register, you will receive a copy of the Commercial Edition of
- the current version of the Publisher. The Commercial Edition is too
- large for convenient distribution as Shareware, and contains licensed
- third-party software not available as shareware. It therefore includes
- the following important features, not found in the Shareware Edition:
-
- <il0.5in><qz>
- *<N>Automatic Optimal Paragraph Composition<QL>
- *<N>Automatic Hyphenation<QL>
- *<N>Graphics (LaserJet & Postscript)<QL>
- *<N>Rubicon's Times, Helv, Classic, Nova and Courier soft fonts<QL>
- <M><M>in wide range of point sizes<QL>
- *<N>Bold Italic soft fonts<QL>
- *<N>Installation Utility for third-party soft fonts<QL>
- *<N>Font compression utilities<QL>
-
- <il><qz>
- You will also receive a printed copy of the complete Reference Manual,
- which provides full documentation of all features of the Publisher,
- together with a glossary of technical terms, a quick reference guide,
- numerous worked examples, and much other useful information which would
- not fit in the Concise Manual included with the Shareware distribution
- files. For period of one year, you will be entitled to purchase all
- program updates, for an update licence fee of $15.00.
-